home *** CD-ROM | disk | FTP | other *** search
- Path: nntp.teleport.com!sschaem
- From: sschaem@teleport.com (Stephan Schaem)
- Newsgroups: comp.sys.amiga.programmer
- Subject: Re: One hardware-basher's manifesto
- Date: 29 Feb 1996 22:36:53 GMT
- Organization: Teleport - Portland's Public Access (503) 220-1016
- Message-ID: <4h59q5$hvl@maureen.teleport.com>
- References: <4ge8na$vhe@ar.ar.com.au> <08000305729070351637@BIRDLAND> <4guenp$1a1@vixen.cso.uiuc.edu> <4h51kg$cio@maureen.teleport.com>
- NNTP-Posting-Host: linda.teleport.com
- X-Newsreader: TIN [version 1.2 PL2]
-
- Stephan Schaem (sschaem@teleport.com) wrote:
-
- : You do not ALWAYS access ram linearly... Drawing a vertical line in 32bit
- : color only accessing ram linearly?
-
- : .. move.l d0,(a0)
- : adda.l a1,a0
- : dbra d0,..
-
- What I really wanted to show (above is a bad example) is that GFX
- function can pretty much access ram 'randomly' for writes & READS.
-
- The 'worse' case senario is free direction texture mapping.
-
- Stephan
-